2016-10-14 - 26780 - Enhancement - Create Universe on PO Cube #Purchasing

ENHANCEMENT

26780 - Create Universe on PO Cube

Purpose

Need to fix the negative Open PO values in Explorer space for PO universe.

Admin Info

Purpose	Need to fix the negative Open PO values in Explorer space for PO universe
Requested By	Mark Harris
Spec Created By	Naveen G
Spec Created Date	10/14/2016
Spec QA by	Uday Kumar P
Objects	ZAFMM_C02
Document Status	Complete

Estimates

SNo	Activity	Estimation in Hours
1	Research	08
2	Documentation	08
3	Development/ Config	40
4	Unit test in DEV	40
5	Unit test in QUA	40
6	Other activity	00
	TOTAL	136

References

Prior Tickets

None

Documents

None

Spec Changes

SNo	Change Details	Requested By	Requested On	Notes if any

Functional Requirement

Purpose/WHY:

Email From Jayson Osmars on 09/24/2016:
There’s a couple things we need from you.
Reviewing the Explorer Friday, the net Price and Value/Cost results weren’t making much sense.
Can we have a more detailed explanation how they are derived and if they are true/correct?

ALSO when do you expect to have the Open Value, Order Value & Received Value objects available in the PO datasource?
We have a meeting Monday afternoon and require the above for the business.

In Scope:

PO Infocube.

Out of Scope:

None

Solution Summary

Negative open values are getting updated into PO cube even after the PO is closed, as delivery costs are getting added to the delivered value.(Open value = Ordered value - Delivered value). So when delivered value is exceeding order value then open value is negative. This is the Standard functionality provided by SAP. Customizing this may take long time & we are not even sure if the changes can be overwritten over the standard logic. There are two ways to handle this:

1. Implementing the logic at universe/WEBI/report level - Considering all PO's as open, if open value is greater than zero. Only the changes to infocube are required at BW end & if the transports can be moved in emergency CM tomorrow to BPQ & BPP. We will start reloading the PO infocube on weekend & the report changes can be delivered by 20/10/2016.

2.Create a new infocube to fetch only Open PO's.This requires 40-80 hrs of development effort, as it involves validation, transports and data reloading.
NEC team approved to work on scenario1.

Test Plan

SNo	Test Scenario	Results
1	Check if the descriptions for Key figures are maintained properly.	Descriptions for Key figures are maintained properly as requested by NEC.
2	Check if the ABAP logic are correctly updated for the key figures.	ABAP logic should work correctly for the key figures.
3	Check if all the objects are collected into the transport requests.	All the objects are collected into the transport request successfully.

Solution Details

1. Create new key figures for Ordered PO value ZORDPOVAL, Open PO value ZOPNPOVAL & Delivered PO value ZGRDPOVAL.
2. Replaced the standard key figures with the customized key figures in the PO infocube ZAFMM_C02.
3. Replace the standard key figures with the customized key figures in the BEx Queries based on PO infocube ZAFMM_C02.
4. Validate the changes in BPD & BPQ.
5. Reloaded the PO infocube once all the transport changes got moved to Production.
6. Created the regional versions for PO Universe.

Issues

Negative open values is due to the logic in standard PO infocube. Customizing this source may take long time & not even sure if the customized changes can be overwritten over the standard logic.